Avax with prefix #359
Merged
Avax with prefix #359
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AVAX uses bech32 for its X & P chains. A valid address format includes the 'X-' or 'P-' ID prepended to the address. This adds a custom decoder to strip the ID and decode the leftover address with bech32. Change is backwards compatible with existing functionality.
The Avalanche C-Chain (AVAXC) uses the EVM addressing system. That being said, on Avalanche, it is valid to have the chain ID prepended to the address. This decoder does some preparsing to strip the ID and pass the leftover address to a decoder.
This reverts commit 8f74a34.
This was referenced Aug 10, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Modified version of #340 (AVAXC uses chainId in the separate PR)